Apparatus for and method of creating a device page for a device which does not support a predetermined protocol on a home network

ABSTRACT

In a home network to which a client device and a plurality of server devices are connected, using a web browser in a client device and determining whether the plurality of devices are devices which support protocols required by the client device, respectively. Accessing the plurality of devices and obtaining and receiving a corresponding Internet protocol address through a process for receiving a predetermined Internet protocol address for each of the accessed devices is a device which supports the desired protocols. Receiving an address determined by the client device for each of the accessed devices which does not support the desired protocols. Creating a device page for displaying the plurality of devices, by arranging the addresses on the web browser.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims the benefit of Korean Application No. 98-16143,filed May 6, 1998, in the Korean Patent Office, the disclosure of whichis incorporated herein by reference.

BACKGROUND OF THE INVENTION

The present invention relates to a home network, and more particularly,to a method of creating a device page when connecting a device whichdoes not support a predetermined protocol to a home network. Recently,various digital devices, such as digital TVs (DTV), digital videocameras (DVC), digital video disk players (DVDP), digital set top boxes,etc. have become popular. The IEEE 1394 standard approved by the IEEEcommittee is attracting attention as a digital network interface toestablish a home network connecting these devices. Generally, every homeappliance provides a method of allowing a user to control variousfunctions using control buttons or a remote controller.

Control between devices meeting the IEEE 1394 standard is made usingcontrol commands. The most representative control command is anAV/Control Command and Transaction Set (AV/C CTS). For such inter-devicecontrol, the functions of each device are defined by hexadecimal codes.For example, the play command for a VCR is defined as “OxC8”.

In a digitized home network system using the IEEE 1394 network,inter-device control is made by organizing one device (the subject ofcontrol) as a control device and a plurality of devices, (targets ofcontrol) as object devices. This type of home network system has thefollowing defects. First, the single control device must know all thecommand sets of the object devices, which causes a considerable softwareand hardware burden. Second, the control device only knows commands inexistence at the time when the product is manufactured. Thus, thecontrol device cannot control new object devices. Third, it is difficultto provide a graphical user interface (GUI). That is, it is difficult tobasically define unified GUI which can be applied to all kinds ofdevices, also there is a limit in defining the GUIs by groups ofproducts.

A method to solve these problems by removing spacial restrictions inmanipulating various devices and effectively display a variety ofinformation by adopting web servers in devices adopting the IEEE 1394,has been studied. Basically, an IEEE 1394 device having a display devicesuch as a DTV or a PC includes a web browser, enabling control of IEEE1394 devices which include a web server. The web browser produces adevice page with links to the IEEE 1394 devices with web servers.However, when a device, not supporting the Internet protocol (IP), or adevice, supporting only specific IP protocols defined by a home networkmanufacturer, has been connected to a home network, no methods orapparatus for treating such device have been proposed.

SUMMARY OF THE INVENTION

To solve the above problem, it is an objective of the present inventionto provide a method of creating a device page which allows a user todiscriminate devices not supporting a predetermined protocol, and whichallows the user to appropriately deal with devices not supportingpredetermined protocols connected to a home network.

Accordingly, to achieve the above objective, there is provided a devicepage creating method using a web browser in a client device, in a homenetwork to which a client device and a plurality of server devices areconnected, the method comprising the steps of: determining whether theplurality of devices are devices which support protocols required by theclient device, respectively, by accessing the plurality of devices;obtaining and receiving a corresponding Internet protocol addressthrough a process for receiving a predetermined Internet protocoladdress, if each of the accessed devices is a device which supports thedesired protocols, and receiving an address determined by the clientdevice if each of the accessed devices is a device which does notsupport the desired protocols; and creating a device page for displayingthe plurality of devices, by arranging the addresses on the web browser.

BRIEF DESCRIPTION OF THE DRAWINGS

The above objective and advantage of the present invention will becomemore apparent by describing in detail a preferred embodiment thereofwith reference to the attached drawings in which:

FIG. 1 is a block diagram of a home network environment.

FIG. 2 is a diagram of a protocol stack of a device operating as a webserver.

FIG. 3 is a flowchart of a method of creating a device page, accordingto the preferred embodiment of the present invention.

FIG. 4 is a diagram of a device page produced by the method of creatinga device page according to the preferred embodiment of the presentinvention.

DESCRIPTION OF THE PREFERRED EMBODIMENT

A digitized home network environment comprised of IEEE 1394 apparatuses,and the protocol stack of a device including a web server, will first bedescribed in brief.

FIG. 1 is a block diagram of a home network environment. A DTV 102, aDVCR 104, a DVDP 106, a DVC-108, a camcorder 110, etc. are all connectedto each other via an IEEE 1394 bus, creating a home network system.Here, the DTV 102 (or another display device such as a PC) includes astorage medium 102 a storing programs and data, described hereinbelow,including a web browser and operates as a client device. The DVCR 104,the DVDP 106, and the DVC 108 each include a web server and operate asserver devices.

FIG. 2 is a diagram of a protocol stack of a device, such as the DVCR104, the DVDP 106, and the DVC 108, operating as a web server. Referringto FIG. 2, the shaded portions of the stack are included in the IEEE1394 apparatus, but the copy protection portions are optional. Morespecifically, the IEEE 1394 protocol uses an asynchronous layer 202, anisochronous layer 204 and an IEC-61883 layer 206. A copy protectionlayer 208 is optional. The IEEE 1394 apparatus can operate as a webserver on the Internet by stacking an IP over the IEEE 1394 layer 210,and including an IP and address resolution protocol (ARP) layer 212, atransmission control protocol (TCP) layer 214 and a user datagramprotocol (UDP) layer 216. The IEEE 1394 apparatus operates as ahypertext transfer protocol (HTTP) server, i.e., a web server, using anHTTP layer 218 and has a hypertext markup language (HTML) texthierarchy, for providing access to control functions, stored in HTMLfiles 222. Associated graphic, sound, video, etc. files are stored inthe bitstream section 226. A user can control devices having web serversby accessing the web pages using a web browser included in a clientdevice, such as the DTV 102.

Referring back to FIG. 1, the DTV 102 (a client device) makes a devicepage by displaying an indication (such as an icon) for all serverdevices connected to a home network whenever there is a state changecaused by a bus reset (including powering on of a device). Each of theserver devices has a unique bitmap file or unique icon file, stored inthe bit stream section 222 (FIG. 2), which represents the device itself.These files can be used by a client device having a web browser toconstruct a device page which displays devices connected to the IEEE1394 network. Here, each icon, shown by the web browser on the screen ofthe client device, is connected to the uppermost level HTML page (or“home page”) of each of the server devices according to a created devicepage.

Referring also to FIG. 2, the respective unique IP addresses are storedin a network information section 224 of each server device. The IPaddresses for all devices connected to the home network may be called,and the unique icon files for all the devices are read from theaddresses, to produce the device page. Here, the client device and theserver devices support both the Internet protocol (IP) and a specificprotocol defined by a home network manufacturer, such as Dynamic HostConfiguration Protocol (DHCP 220), so that the client device can receivethe icon files from each of the server devices. That is, the clientdevice and the server devices support IP and HTTP, and if necessaryDHCP.

However, for example referring to FIG. 1, if the camcorder 110,connected to the home network via the IEEE 1394 bus, satisfies only theIEEE 1394 standard and does not have a web server (no HTTP), it will bedifficult to display the camcorder 110 as an icon when the client devicecreates a device page using a web browser. Or, if the camcorder 110 doesnot support the specific protocol defined by the home networkmanufacturer (DHCP), even though it includes a web server, it also willbe difficult to display the camcorder 110 as an icon.

A device page creating method according to the present invention tosolve the above problems will now be described as follows.

FIG. 3 is a flowchart of a method of creating a device page, accordingto the preferred embodiment of the present invention. Since the devicepage is produced whenever the bus is reset, first, a determination ofwhether a bus is reset is made in step 302. Upon detection of a busreset, a client device (DTV 102 of FIG. 1), having a web browser, startsthe process of producing a device page. In step 304, a plurality ofserver devices, connected to a home network, are accessed to obtaintheir IP addresses. Typically, the IP addresses of server devices areobtained through a process of receiving predetermined IP addresses. Theweb browser reads an icon file, e.g., “icon.gif”, from each of the IPaddresses, to present a user with recognizable icons. However, when adevice not supporting the IP and HTTP is detected, a separate treatmentprocess is required.

Thus, in step 306, a plurality of server devices are accessed todetermine whether the devices support IP. A determination of whether theaccessed server devices observe the IP over the 1394 standard can bemade by reading a network channel register (NCR), i.e., by performing anasynchronous reading transaction. If in step 306 each device supportsIP, it is determined whether each of the accessed server devicessupports the HTTP in step 308. Here, the determination of whether theaccessed server devices support the HTTP can be made, for example, byreading a predetermined register pre-defined in a control and statusregister (CSR) area to discriminate a device satisfying a protocoldesired by a home network manufacturer. Alternatively, thisdetermination can be made by demanding a specific file (e.g., anattribute file) from each of the server devices via the HTTP and thenchecking the response of the server devices.

If, in step 308, each device also supports HTTP, the IP addresses of theaccessed server devices are obtained through the process for receiving apredetermined IP address, since each of the accessed server devicessupports the desired protocols in step 310. For example, the IP addresscan be obtained from the accessed server devices, or can be preallocatedin the client device. Alternatively, new addresses can be allocated.Meanwhile, for server devices not supporting the IP (determined in step306) and those not supporting the HTTP (determined in step 308), theclient device obtains IP addresses, for each such device, in step 312.That is, addresses set by the client device are obtained. After step 310or 312, the web browser produces a device page for displaying aplurality of server devices, by arranging the obtained addresses in step314.

Next, in step 316, a web browser shows the produced device page on theweb browser at a predetermined condition time. Here, server deviceshaving unique IP addresses are displayed as unique icons obtained by theaddresses, but devices having no unique IP addresses are displayed asdefault icons pre-programmed in the client device.

FIG. 4 is a diagram of a device page produced by the method of creatinga device page according to the preferred embodiment of the presentinvention. Referring to FIG. 4, a web browser screen 404 is shown on adisplay screen 402 of, for example, a DTV operating as a client device,and icons 406, 408 and 410 of a plurality of server devices connected toa home network are shown according on a device page. For example, if thecamcorder 110 of FIG. 1 does not support IP, a default icon 412,prepared in the client device, as shown in FIG. 4 is displayed and thecamcorder 110 is treated as an unknown device.

If a user selects the DVCR icon 406, the web browser is connected to theuppermost level HTML page (home page) of the DVCR 104, acting as a webserver, and reads the content from the page. However, if the userselects the default icon 412, the web browser is connected to apre-programmed default page (should one exist), stored in the storagemedium 102 a on the client (DTV 102), and the content of a default pageare displayed. That is, information on the unknown device to bedisplayed on a device page is possessed by the client device. If theclient device does not have display information for a device, a messagewill inform the user that the device having the default icon cannot beaccessed by the client.

In the case of devices which can be recognized by the client devicebecause of their pre-stored display information, the client deviceprovides a control command usage by means of a remote controller to thedefault page so that a user can control the basic functions of thedevices by executing control commands such as an existing AV/C CTS.

The above-described embodiment of the present invention can be writtenby a program which can be executed by a specific purpose computer or ageneral purpose digital computer which operates the program from acomputer readable media used in the computer. Such computer readablemedia can include storage media such as a variety of memory chips (e.g.,RAM, ROM, DRAM, etc.), a magnetic storage medium (e.g., floppy disks,hard disks, etc.), an optical reading medium (e.g., CD-ROMs, DVDs,etc.), and carrier waves (e.g., transmission through Internet or othernetwork protocol).

The recording medium stores program codes for allowing some steps to beperformed in a computer, for example: determining whether a plurality ofdevices are devices which support protocols required by a client device,by accessing the plurality of devices; obtaining corresponding IPaddresses through a process for receiving a predetermined IP address, ifeach of the accessed devices is a device which supports the desiredprotocols, and obtaining an address set by the client device if each ofthe accessed devices is a device which does not support the desiredprotocols; and creating a device page for displaying the plurality ofdevices, by arranging the addresses on a web browser. The program may becoded so as to determine whether the accessed device is a device whichsupports the IP, by reading the network channel register of the accesseddevice, as in the determination step, and to make another determinationof whether the accessed device is a device which supports a protocoldefined by a home network manufacturer, by reading a pre-definedspecific register, if the accessed device is the device which supportsthe IP.

Functional programs, codes, and code segments for accomplishing thepresent invention can be created by programmers skilled in the art towhich the present invention pertains without undue experimentation.

In the device page creating method according to the present invention asdescribed above, when a device not supporting predetermined protocols isconnected to a home network, devices not supporting predeterminedprotocols are identified, to allow a user to discriminate such a deviceand to support the user in coping with the unsupported device.

1. An IEEE 1394 complaint TV comprising: an IEEE 1394 bus compliantnetwork interface; a storage medium storing programs and data aboutnon-compliant devices which may be connected to the IEEE 1394 bus, theprograms comprising: a web browser software that reads registers of eachdevice and/or demands a predefined file from each device connected tothe IEEE 1394 bus, according to the read registers and/or the demand theweb browser determines and accesses each IP and HTTP compliant deviceconnected to the IEEE 1394 bus and displays a web page linking icon to atop level web page served by each connected IP and HTTP compliantdevice, for non-compliant devices connected to the bus, accesses thestorage medium to assign a default IP address and displays a web pagelink to the programs and the data about the non-compliant device,including creating a web browser display page displaying an indicationfor devices for which no such programs and data exists.
 2. A computerreadable medium, for a web browser enabled client device in a homenetwork, containing software for causing the client device to performthe following actions: accessing a plurality of server devices connectedto the client device in the home network; reading a network channelregister of each server device; determining if each server devicesupports IP according to the read network channel register; reading acontrol and status register of each server device; determining if eachserver device supports HTTP according to the read control and statusregister; for each server device which supports IP and HTTP obtaining anIP address; for each server device which does not support IP and HTTPassigning a default IP address; creating a web browser device pagedisplaying a web page link to a web page served by each devicesupporting IP and HTTP, and displaying a web page link to default datastored on a medium associated with the client device, for each serverdevice which does not support IP and HTTP.
 3. A computer readablemedium, as set forth in claim 2, wherein the data on the mediumcomprises pre-defined web pages associated with a sub-set of the serverdevices which do not support IP and HTTP and an indication of lack ofsupport for the remaining server device which do not support IP andHTTP.
 4. A computer readable medium, as set forth in claim 3, whereinthe pre-defined non-supporting server device web pages allow control ofthe associated server devices.
 5. A local area device network forentertainment equipment comprising: a local area device bus; at leastone IP-HTTP compliant server device containing a web server connected tosaid bus, the web server serving web pages allowing control of the atleast one compliant device; at least one non IP-HTTP compliant serverdevice connected to said bus; each client device, connected to said bus,comprising: a storage device containing default upper layer Internetprotocol addresses used over underlying addresses of the bus and webpages for at least some of the non IP-HTTP compliant devices, thedefault Internet protocol addresses and web pages enabling control ofassociated non IP-HTTP compliant devices; a programmed computerprocessor reading predetermined registers of each server device and/ordemanding a predefined file from each server device, determining the IPand HTTP compliance and non-compliance of each server device accordingto the reading and/or the demanding; a web browser displaying a web pagelink to a top web page on each web server of each IP-HTTP compliantdevice, displaying a web page link to a top web page in the storagedevice if the at least one IP-HTTP compliant device has an associateddefault web page, and displaying a web page link to an indication thatcontrol is not possible if the at least one non IP-HTTP compliant devicedoes not have an associated default web page.